Summary

Interface "Filter items by can_contain L:, V:, M: (longest_side, volume, mass); affects AIM, inventory…"

Purpose of change

• Resolve Filter items with pockets by pocket's length, weight, volume #74635 (this is the second part).

Describe the solution

• Similar to Crafting GUI: Filter recipes by what can fit into the result (longest_side, volume, mass) #78384 with key differences:
  • Store the fake items and their itype in the lambda capture, instead of static variable local to the file.
  • Failure cannot generate a popup with a helpful message. At least not always, so it never does. The reason is in AIM the filter is applied on each keystroke of L:122 cm and we cannot throw 6 popups at the player when they write :122 c.
    • Subject to change. It would be better if hinted.

Describe alternatives you've considered

• Share the template code with Refactor filters in crafting GUI to use a template #78518. The use cases are different enough, so the template would be too complicated.
• Fully implement displaying the helpful hint in every relevant menu.
• Make AIM not live (update after each keystroke when writing a filter). And show a hint popup when the filter is finished and invalid.
• Hook up to AIM and only show the helpful hint on an invalid filter after the player enters ENTER denoting "I am finished with the filter." Answering the question "Why doesn't it work?"
  • I didn't bother with this now, could be cool.
  • Should be implemented for all the other menus too.

Testing

Use the filters in

• AIM
• V List all items around the player
• a Use item

Additional context

• Without AIM cache filter function once #78480 this would be too slow in AIM.
• This part could be implemented in item_controller as item_controller::get( const itype & ). It would be more efficient, this passes all items:

item_controller->find( [](
    const itype & i ) {
        return i.get_id() == STATIC( itype_id( "debug_item_search" ) );
    } )[0]